Cruncher Processing

Cruncher processing can be roughly divided into three stages:

Seed Case Processing

Perform any user-configured case sanitation, validation, or normalization using AUX scripts to prepare initial cases for the application of time-varying data

If a valid Cache case exists with an ID reflecting the current configuration, use that and do not re-process
Otherwise, load all AUX/HDBExport files in the optional “pre” subdirectory
Load a source case (PWB, AUX, or HDBExport). More recently modified source cases are used first
Load all AUX/HDBExport files in the optional “post” subdirectory
Attempt to solve the resulting case.
- If the case does not solve, start over using the next most recently modified source case in the directory
If the case solves, save a Cache Case with a name reflecting the source case used, and a hash-based ID generated from the current configuration

Snapshot Processing

Use time-varying data inputs to apply specific modifications to a Seed Case and generate a solved power flow representing the case stat at a given time, saved as a Snapshot Case

Snapshot processing begins with a Seed Case. The same Seed Case may be used for any number of Snapshots
Cruncher loads specified Time Inputs to map relevant data to each Snapshot
Processing Phases performed in sequence
The resulting power flow states are solved and saved as Snapshot Case PWBs
If configured to do so, an xlsx Snapshot Report is generated and saved

Analysis

Perform Contingency or other analysis on one or more Snapshot Cases

Analysis of a given Snapshot begins by loading the Snapshot Case. If the Snapshot itself failed to solve, Analysis will not be performed
Analysis currently supports two phases
- Analysis AUX phase runs a user-specified AUX script
- Contingency Analysis phase runs Contingency Analysis on the case
Resulting state is saved as an Analysis Case PWB
If configured to do so, an XLSX Analysis Report is generated and saved